Repository navigation
Conversation
atomic-saas deploys staging only when started by hand since its PR 148, so deploy_staging.yml no longer listens for the atomic-server-develop event and this workflow's dispatch reached nothing. To test an atomic-server branch there, start Deploy to staging in atomic-saas with atomic_server_ref set to it. ATOMIC_SAAS_DISPATCH_TOKEN stays: main.yml's Downstream job still uses it to read atomic-saas.
The ci job had no timeout-minutes, so GitHub's 6-hour default applied. On 2026-09-25 both Mancave CI jobs (develop run 4587 and batch run 4591) stopped logging at the same minute, mid e2e, and would hold both runners until that default released them. A full run takes 45 to 75 minutes; 150 leaves room for a cold per-runner cache. The images job already has 120.
pnpm/action-setup defaults to ~/setup-pnpm, which every runner on a host shares. On 2026-09-25 develop run 4596 failed at Install pnpm with ENOTEMPTY because the batch's Downstream job on the other Mancave runner was installing into the same directory at the same second. Point dest at runner.temp in the two jobs that run on Mancave.
|
Reopened. Batch #1773 carried this PR at 467f182, so the staging-dispatch removal and the CI timeout are on develop. The last commit, f7b03bd ("give each runner its own pnpm"), is not. It goes into the next TrekMeester batch. Generated by Claude Code |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 37585749 | Triggered | Generic Password | cb4cc98 | lib/src/vault/secret_envelope.rs | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
The red GitGuardian check is not from this PR's change. It flags Generated by Claude Code |
|
Landed on develop in 46562ff via the combined batch #1828 (green on Mancave, run 4639). Closing. Generated by Claude Code |
Requested by Joep · project thread
Before: pnpm installs into
~/setup-pnpm, and every runner on the same host shares that directory. On 2026-09-25, develop run 4596 failed at "Install pnpm" withENOTEMPTYbecause another runner's job was installing there at the same second.After: each job installs pnpm into its own runner's temp directory, so two runners on one host no longer collide.
How: sets
dest: ${{ runner.temp }}/setup-pnpmon the two pnpm steps that run on Mancave: thecijob inmain-ci.ymland the Downstream job inmain.yml. This PR originally also removed the staging dispatch and added the 150-minute CI timeout. Both of those landed in TrekMeester batch #1773, and develop has been merged into this branch, so only the pnpm change is left.